vulkanpushconstants: Don't report invalid ranges
authorGeorges Basile Stavracas Neto <georges.stavracas@gmail.com>
Wed, 4 Jan 2017 17:37:02 +0000 (15:37 -0200)
committerBenjamin Otte <otte@redhat.com>
Wed, 4 Jan 2017 17:40:42 +0000 (18:40 +0100)
Vulkan doesn't accept empty ranges, so simply don't report
them.

gsk/gskvulkanpushconstants.c

index f7daf1acbfab9c9394fc72917e5d80e7278ec760..34574c2532459dfa673778c256d438bed9bec6c7 100644 (file)
@@ -101,13 +101,13 @@ gsk_vulkan_push_constants_push_fragment (GskVulkanPushConstants *self,
 uint32_t
 gst_vulkan_push_constants_get_range_count (void)
 {
-  return 2;
+  return 1;
 }
 
 const VkPushConstantRange *
 gst_vulkan_push_constants_get_ranges (void)
 {
-  static const VkPushConstantRange ranges[2] = {
+  static const VkPushConstantRange ranges[1] = {
       {
           .stageFlags = VK_SHADER_STAGE_VERTEX_BIT,
           .offset = G_STRUCT_OFFSET (GskVulkanPushConstantsWire, vertex),